|
In software engineering, a resource-oriented architecture (ROA) is a style of software architecture and programming paradigm for designing and developing software in the form of resources with "RESTful" interfaces. These resources are software components (discrete pieces of code and/or data structures) which can be reused for different purposes. ROA design principles and guidelines are used during the phases of software development and system integration. REST, or Representational State Transfer (), describes a series of architectural constraints that exemplify how the web's design emerged. Various concrete implementations of these ideas have been created throughout time, but it has been difficult to discuss the REST architectural style without blurring the lines between actual software and the architectural principles behind it. In Chapter 5 of his thesis, Roy Fielding documents how the World Wide Web is designed to be constrained by the REST series of limitations. These are still fairly abstract and have been interpreted in various ways in designing new frameworks, systems, and websites. In the past, heated exchanges have been made about whether RPC-style REST architectures are RESTful.〔Chapter 5 of Fielding's dissertation is ("Representational State Transfer (REST)" ).〕 == Guidelines for clarification == The Resource Oriented Architecture as documented by Leonard Richardson and Sam Ruby gives concrete advice on specific technical details. Naming these collections of guidelines "Resource Oriented Architecture" may allow developers to discuss the benefits of an architecture in the context of ROA. Example guidelines include: * Query string parameters in the URI are appropriate if they are inputs to a Resource which is an algorithm * * Otherwise, these values should be placed into the path component of the URI * Prefer pragmatic uses of putting data into URI, instead of using HTTP Headers * * A resource can use file extension in the URI, instead of Content-Type negotiation * RPC-style APIs are avoided in favor of Resources and protocols * A representation of a resource should have many links to the other Resources in the application, so that a client can discover state transitions * URI templates provide the technology behind specifying families of URI to clients . 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Resource-oriented architecture」の詳細全文を読む スポンサード リンク
|